@fitz-vivodyne Thanks for the PR and sorry about the delay here. I've just let the tests run, and there are some failures. I believe this has the same cause as #1116 (review), and I think the option needs to be added to the action.yml file.

Thanks @tgummerer, just pushed the updates to action.yml

Hello 👋 Thanks for doing this, @fitz-vivodyne!

I am wondering what you think of keep using the refresh argument, and change the behavior of it to use this?

For most users they expect to be using this way of refreshing. We need to bump major, since it might break things, but it's the same kind of breaking we've done since v2; smaller and easy to migrate.

I am wondering what you think of keep using the refresh argument, and change the behavior of it to use this?
For most users they expect to be using this way of refreshing. We need to bump major, since it might break things, but it's the same kind of breaking we've done since v2; smaller and easy to migrate.

@simenandre I found the current behavior surprising and when I first started using the action I 100% expected the refresh argument to just run with the --refresh flag.
If you actually want to run a pulumi refresh I would expect to run that as a standalone action/command.

Agreed that a major version bump would be appropriate, and I'm personally supportive of fully replacing the refresh functionality.

Thoughts on moving forward?
New PR, modify this one to strip out the refresh behavior?

I think a new major release and changing the refresh functionality would make sense here as well. I think updating this PR sounds good, but no strong preferences here either way.

+1 to changing the refresh functionality and bumping the major version. I'm guessing the reason it behaved this way originally was because automation api didn't have support for the refresh flag.

Although, now that I think about it, I think we've only added support for --refresh for Go Automation API so far, so we'll need to port that over to the nodejs automation api to be able to be used here.

EDIT: Looks like we at least have the refresh option for up and preview in nodejs automation api, but would be great to get this supported for destroy as well to have consistency across commands.

@tgummerer I think we should provide the guidance for what we want to happen here. Let's make the decision and try to land this PR, or decide not to land it and describe the alternative.

I'd be happy to land this PR if @fitz-vivodyne wants to update it with the updated refresh functionality. Once that's done I can approve, merge and create a new release with a major version bump.

@fitz-vivodyne Will you have time to take another step on this PR?

Sorry, haven't had bandwidth recently.
Might be a while before I'm able to get around to it, anyone else can feel free to grab it if they're available

@fitz-vivodyne Do you mind converting it to a Draft PR for now, so that it doesn't show up in our review queue?

Alright, I find myself wanting this functionality again so I just pushed the discussed changes to the PR.

This now represents a breaking change/major release that would change the behavior of refresh: true to run commands with --refresh instead of running pulumi refresh && pulumi <command>

This PR has been shipped in release v6.0.0.

@fitz-vivodyne @tgummerer as long as the effect of this change on pulumi preview has been explained and is clear to me' what is the change to pulumi up command? Is that just for consistency but we expect the same effect, with precison to maybe error-handling, or there is a significant difference in behavior too?

I believe this info should be included in the 'Migration from v5 section of the readme'. I think most people care about the actual behavior change than what is updated in the implementation.